home *** CD-ROM | disk | FTP | other *** search
Text File | 1989-10-16 | 4.7 KB | 130 lines | [TEXT/PJMM] |
- {
- THINK Pascal 2.03
- Release Notes
- 10/16/89
-
- This is an update that fixes bugs in THINK Pascal 2.0.
-
- WHO NEEDS THIS UPDATE
- =====================
- THINK Pascal 2.0 users who have not upgraded to THINK Pascal 2.01.
- THINK Pascal 2.0 users who plan to use the Apple Macintosh Portable or
- the Apple Macintosh IIci.
-
- This 2.03 update is identical to the 2.01 update, with two additional
- bug fixes: with 2.01, choosing the Go command to run a program within
- the THINK Pascal environment would crash on the Apple Macintosh Portable
- and the Apple Macintosh IIci. 2.03 fixes both of these problems. (The
- 2.02 update, which we released a month ago, runs on the Portable, but
- not on the IIci.)
-
- For a complete description of all the bugs that this update fixes,
- read the section ╥WHAT╒S IN THIS UPDATE╙ below.
-
- INSTRUCTIONS
- ============
- The patch program, ╥THINK Pascal => 2.03╙, transforms your version 2.0
- (or later) into version 2.03.
-
- 1. Replace your existing Runtime.lib and ╡Runtime.lib files with
- the new ones included in this update.
-
- 2. Double-click on the application ╥THINK Pascal => 2.03╙. Click on the
- Update THINK Pascal button. Use the standard file dialog to find
- your current copy of THINK Pascal. Click on the Patch button.
-
- 3. Your THINK Pascal application will be upgraded to version 2.03.
-
- INFORMATION
- ===========
- For further information, or to obtain the patch in another format,
- please contact:
-
- David Allcott
- Symantec Corp.
- 135 South Rd.
- Bedford MA 01730
- (617) 275-1710
-
- AppleLink address:X0121
-
-
- WHAT╒S IN THE UPDATE
- ====================
- The THINK Pascal 2.03 update fixes these bugs:
-
- (1) "Fatigue" bug: THINK Pascal used up about 1K of System Heap space
- every time a program was run, until it ran out and eventually crashed.
-
- (2) On a Macintosh II under System Tools 5.0, THINK Pascal would crash
- with a Bus Error after running a program.
-
- (3) If an INLINE procedure was declared in a nested scope, an erroneous
- "MOVE.L A6,-(A7)" would be inserted into the inline code whenever the
- procedure was called.
-
- (4) The SQR function would generate incorrect code for integer arguments.
-
- (5) When indexing a multi-dimensional array whose total size was >32K,
- an illegal instruction would frequently be generated in place of "EXT.L Dn".
-
- (6) The ODD function would sometimes yield a Code Generator Error.
-
- (7) INSERT(s,d,i) would not work if i was the last position in d.
-
- (8) If SEEK was used to position the file buffer to the end of file, any
- subsequent SEEKs to the middle of the file will still yield EOF.
-
- (9) READ(f,c) where f is TEXT and c is CHAR would not read past the
- end of line.
-
- (10) Boolean expressions involving "&" and "|" would generate incorrect
- code for floating-point operands if the 68881 option was checked.
-
- (11) Using a pop-up menu (e.g. command-click in the title bar of a window)
- on any screen other than the main screen confused the Menu Manager and
- usually crashed the system.
-
- (12) If a program running under the debugger called "EventAvail" with a
- mask which included activate events, it would hang forever.
-
- (13) If you TRANSFER under Finder, and there are some unsaved edits,
- and you CANCEL from the "Save changes before transferring" dialog, it
- goes ahead and transfers anyway, without saving the files.
-
- (14) READLN from the Text window would confuse the scrolling: the thumb
- would move but the text wouldn't scroll.
-
- (15) Typecasting 2 variables from different files in the Lightsbug window
- would crash.
-
- (16) Printing to a Laserwriter IISC would only print in Monaco 12,
- regardless of the current font.
-
- (17) Files which contain control characters (whose ordinal value was less
- than 32 decimal) would confuse the editor, leaving great white gaps in the
- windows and causing text to be lost.
-
- (18) Clicking too quickly on the spray can would cause a crash, or yield an
- "Illegal Instruction" error on subsequent runs.
-
- (19) On the Apple Macintosh Portable, attempting to run a program by
- choosing the Go command would crash.
-
- (20) On the Apple Macintosh IIci, attempting to run a program by
- choosing the Go command would crash.
-
-
- The files "_r_char.lib" and "_fseek.lib" are provided for users who need
- to customize the runtime libraries, i.e. to make them smaller. You should
- open any customized versions of the "Runtime.╣" project, and replace
- "_r_char.lib" and "_fseek.lib" with the new files. To do this,
- option-double-click on these files in the project window, and select the
- new versions from the standard file dialog. Then, use BUILD LIBRARY to
- build the corrected custom "Runtime.lib". If you intend to customize the
- library in the future, you may want to update the original project document
- as well.
-
- If you have any customized versions of "╡Runtime.╣", you should update them
- in the same fashion; note that "_fseek.lib" is not needed for this library.
- }